Method and system for recording a transaction using a dynamic user interface within an application

ABSTRACT

A method for recording a transaction using a Dynamic User Interface (DUI) within an application, including receiving, from a user of the application, the transaction relating to a customer of the user; receiving a request to generate a form for the transaction; generating, based on the request to generate the form, the form containing a customer list and a form element; receiving a request to generate the DUI; generating, based on the request to generate the DUI, the DUI adjacent to the form displayed within the application; receiving an identification of the customer from the customer list; populating, based on the identification of the customer, the DUI with the transaction relating to the customer; receiving, from the user, a selection of the transaction from the DUI; populating, within the form adjacent to the DUI, the form element using the transaction; and recording, within the application, the transaction.

BACKGROUND

When a business owner (i.e. user) fills out a form relating to atransaction in a website or application, the user may often be requiredto obtain disparate pieces of information from various sources (e.g.customer data, bank data, expense data), and then input these pieces ofinformation into the form. This can be a time consuming and manuallyintensive process, involving many steps and a lot of navigating betweenapplications of different parts of one application. Often times, even ifthe data exists in the application, there is no way for the user tointelligently add the data to a form based on the context of the form.

SUMMARY

In general, in one aspect, the invention relates to a method forrecording a transaction using a Dynamic User Interface (DUI) within anapplication. The method includes receiving, from a user of theapplication, the transaction relating to a customer of the user;receiving, from the user and within the application, a request togenerate a form for the transaction; generating, based on the request togenerate the form and within the application, the form containing acustomer list and a form element; receiving, from the user and withinthe application, a request to generate the DUI; generating, based on therequest to generate the DUI, the DUI adjacent to the form displayedwithin the application; receiving, from the user and within the formadjacent to the DUI, an identification of the customer from the customerlist; populating, based on the identification of the customer, the DUIwith the transaction relating to the customer, where the transaction isowned by an application operator; receiving, from the user, a selectionof the transaction from the DUI; populating, within the form adjacent tothe DUI, the form element using the transaction; and recording, withinthe application, the transaction.

In general, in one aspect, the invention relates to a system forrecording a transaction using a Dynamic User Interface (DUI). The systemincludes a first service provider server containing: a computerprocessor, and an application executing on the computer processor, withfunctionality to perform: receiving, from a user of the application, thetransaction, from outside the service provider server, relating to acustomer of the user, receiving, from the user and within theapplication, a request to generate a form for the transaction;generating, based on the request to generate the form and within theapplication, the form containing a customer list and a form element;receiving, from the user and within the application, a request togenerate the DUI; generating, based on the request to generate the DUI,the DUI adjacent to the form displayed within the application;receiving, from the user and within the form adjacent to the DUI, anidentification of the customer from the customer list; populating, basedon the identification of the customer, the DUI with the transactionrelating to the customer, where the transaction is owned by anapplication operator; receiving, from the user, a selection of thetransaction from the DUI; populating, within the form adjacent to theDUI, the form element using the transaction; and recording, within theapplication, the transaction. The system also includes a second serviceprovider server communicatively coupled to the first service providerserver and containing a data repository storing the transaction.

In general, in one aspect, the invention relates to a non-transitorycomputer readable storage medium storing instructions for recording atransaction using a Dynamic User Interface (DUI) within an application,the instructions executable on a computer processor and containingfunctionality for: receiving, from a user of the application, thetransaction relating to a customer of the user; receiving, from the userand within the application, a request to generate a form for thetransaction; generating, based on the request to generate the form andwithin the application, the form containing a customer list and a formelement; receiving, from the user and within the application, a requestto generate the DUI; generating, based on the request to generate theDUI, the DUI adjacent to the form displayed within the application;receiving, from the user and within the form adjacent to the DUI, anidentification of the customer from the customer list; populating, basedon the identification of the customer, the DUI with the transactionrelating to the customer, where the transaction is owned by anapplication operator; receiving, from the user, a selection of thetransaction from the DUI; populating, within the form adjacent to theDUI, the form element using the transaction; and recording, within theapplication, the transaction.

Other aspects of the invention will be apparent from the followingdescription and the appended claims.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 shows a system in accordance with one or more embodiments of theinvention.

FIGS. 2A and 2B show flowcharts in accordance with one or moreembodiments of the invention.

FIGS. 3 and 4 show examples in accordance with one or more embodimentsof the invention.

FIG. 5 shows a computer system in accordance with one or moreembodiments of the invention.

DETAILED DESCRIPTION

Specific embodiments of the invention will now be described in detailwith reference to the accompanying figures. Like elements in the variousfigures are denoted by like reference numerals for consistency.

In the following detailed description of embodiments of the invention,numerous specific details are set forth in order to provide a morethorough understanding of the invention. However, it will be apparent toone of ordinary skill in the art that the invention may be practicedwithout these specific details. In other instances, well-known featureshave not been described in detail to avoid unnecessarily complicatingthe description.

In general, embodiments of the invention provide a system and method forrecording a transaction using a Dynamic User Interface (DUI) within anapplication. Specifically, a DUI is displayed next to a form in agraphical interface (GUI). The DUI contains data relating to the form,and is context sensitive. In other words, the data in the DUI relates tothe context of the form. For example, if the form relates to an invoiceof a specific customer, the data in the DUI may relate to the invoice ofthe customer. In most embodiments of the invention, the DUI does notcover or block the form, but appears next to it, so that a user may seeall relevant information in one view. The form and DUI may appear in agraphic interface in a desktop computing device, or a mobile device.

FIG. 1 shows a system (100) in accordance with one or more embodimentsof the invention. As shown in FIG. 1, the system (100) includescomponents such as a service provider server A (110), a softwareapplication (112), a service provider server B (116), a data repository(117), a display (130), and a GUI (131). These components are describedbelow and may be located on the same device (e.g. a server, mainframe,desktop Personal Computer (PC), laptop, Personal Digital Assistant(PDA), telephone, mobile phone, kiosk, cable box, glasses device, andany other device) or may be located on separate devices connected by anetwork (e.g. the Internet, a wide area network (WAN), or a local areanetwork (LAN)), with wired and/or wireless segments. In one or moreembodiments of the invention, there may be more than one softwareapplication (112) and GUI (131) running on a device, as well as morethan one service provider server A (110), service provider server B(116), and display (130) interfacing with those components.

In one or more embodiments of the invention, a user (105) may be anowner of a business, and uses software application (112) to managebusiness concerns. A third party (106) may be a company, a client, apartner, or any other person or entity related to the user (105). Aninstance A of transaction (107) is any business record (e.g. contract)that may be managed by the user (105) and/or the third party (105). Inother words, the instance A of transaction (107) may be any transactionrelating to the finances and/or business of the user (105). For example,instance A of transaction (107) may be an estimate for work done by thebusiness of the user (105) for a customer. The instance A of transaction(107) may be owned by the user (105), the third party (106), and/or aservice provider (e.g. the owner, developer, and/or manager of thesoftware application (112)).

In one or more embodiments of the invention, a service provider server A(110) may run on a computer processor (111), and is configured to host asoftware application (112). The software application (112) is configuredto perform specific functions to record a transaction using the DUI(132).

The software application (112) may receive input from various sources,including the user (105) and the third party (106). The softwareapplication (112) may store data in and/or access data from a datarepository (117). The service provider server B (116), the softwareapplication (112), and other data stored on the service provider serverB (116) may be owned and/or operated by a service provider (e.g. theowner, developer, and/or manager of the software application (112)).

In one or more embodiments of the invention, the software application(112) is configured to receive the transaction relating to a customer ofthe user. The transaction is related to a business concern of the user.For example, a transaction may be an invoice, a bill, or any otherdocument relating to the business of the user and the customer. In oneor more embodiments of the invention, the software application (112) isfurther configured to receive a request to generate a form for thetransaction. The form is a page that contains input elements that can bemodified or written into (e.g. billing address of a customer). Forexample, a piece of data (i.e. a transaction) may be dragged from theDUI (132) and dropped into an input element of the form.

In one or more embodiments of the invention, the software application(112) is further configured to generate the form containing a customerlist and a form element. The customer list is a list of customers fromwhich a user can select a particular customer. The form element is aninput element into which data can be copied (e.g. dragged and dropped).In one or more embodiments of the invention, the software application(112) is further configured to receive a request to generate the DUI.The DUI is a portion of the GUI that sits to the right of the form andcontains various information that may relate to the selected customer.In one or more embodiments of the invention, the software application(112) is further configured to generate the DUI adjacent to the formdisplayed within the application.

In one or more embodiments of the invention, the software application(112) is further configured to receive an identification of the customerfrom the customer list. The identification and selection of a customermay be, for example, from a drop down list of all the customers of theuser. In one or more embodiments of the invention, the softwareapplication (112) is further configured to populate the DUI with thetransaction relating to the customer, where the transaction is owned byan application operator. For example, transactions may include anythingrelating to the customer such as bills, expenses, payments, and soforth.

In one or more embodiments of the invention, the software application(112) is further configured to receive a selection of the transactionfrom the DUI. The selection may be, for example, a drag and drop motionof the transaction visual from the DUI to the form by the user. In oneor more embodiments of the invention, the software application (112) isfurther configured to populate, within the form adjacent to the DUI, theform element using the transaction. In one or more embodiments of theinvention, the software application (112) is further configured torecord the transaction. Those skilled in the art will appreciate thatthe software application (112) may perform other functions beyond thosedisclosed.

In one or more embodiments of the invention, the service provider serverB (116) is configured to host a data repository (117). The datarepository (117) may contain data associated with the softwareapplication (112). The data repository (117) may be a relationaldatabase that stores data entries associated with the softwareapplication (112). The data repository (117) may also be a spreadsheetcontaining data cells associated with the software application (112). Inone or more embodiments of the invention, the data repository (117) maybe implemented with many technologies. The data repository (117) mayreceive data from various sources, including the software application(112) over a network B (115).

After receiving data from the software application (112), the datarepository (117) may process (i.e. modify, transform, format) the data,and then store the data. The data may include a recurring transaction(118), an expense (119), a timecard (120), an invoice (121), a company(122), and an instance B of the transaction (123). The recurringtransaction (118) may be a transaction that occurs on a specified timeinterval, such as a monthly bill to a customer. The expense (119) may bean expense of the user and/or a customer of the user. The timecard (120)may be a record of the time worked by an employee of the user'sbusiness. The invoice (121) may be an invoice for the customer of theuser (i.e. of the business of the user). The company (122) may be abusiness that is related to the user's business in some manner. Theinstance B of the transaction (123) may be the instance A of thetransaction (107) at a later time, after it has been processed by thesoftware application (112) and stored in the data repository (117).

Those skilled in the art will appreciate that the data repository (117)may receive and store data from other entities beyond the softwareapplication (112), and may perform other functions beyond thosedisclosed. Further, the service provider server B (116), and the datastored on this server may be owned and/or operated by a service provider(e.g. the owner, developer, and/or manager of the software application(112)).

In one or more embodiments of the invention, a display (130) may displaya graphic user interface (i.e. the GUI (131)). The GUI (131) may displayinformation associated with the software application (112). The GUI(131) may be viewed in a web browser, an application window, and thelike. The GUI (131) may be viewed in these display technologies by auser of the software application (112). The GUI (131) may includestandard web elements, including video, audio, and text, as well asinterface technologies not limited to text submission on forms, voicecapture, and user gesture interpretation. In one or more embodiments ofthe invention there may be various other display technologies used byand to view the GUI (131).

The software application (112) may generate the GUI (131), and theelements inside the GUI (131), such as a DUI (132), an instance C of thetransaction (133), a form (134), a customer list (135), and an instanceD of the transaction (136). The DUI (132) is a portion of the GUI (131)that is displayed to the right of the form (134). It contains variouspieces of information relating to the customer, the user, and thebusiness concerns of the user. The data contained in the DUI (132) maybe selected by the user, and dragged and dropped into the form (134).The instance C of the transaction (133) is an example of a data that maybe selected from the DUI (132) and dragged and dropped into the form(134). For example, the instance C of the transaction (133) may be thesame information as instance A of the transaction (107) and instance Bof the transaction (123), but presented at a later time in the GUI(131). In a similar fashion, instance D of the transaction (136) may bethe same data as instance C of the transaction (133), except that it hasbeen copied (e.g. dragged and dropped by a user) into the form (134).The customer list (135) may be a list of customers that is selectable bythe user (105) to identify a specific customer, and potentially toidentify specific transactions related to that customer in the DUI(132). Those skilled in the art will appreciate that there may bevarious other elements of FIG. 1 that have not been described.

FIG. 2A shows a flowchart in accordance with one or more embodiments ofthe invention. The process shown in FIG. 2A may be used, for example,with the system (100), to record a transaction using a Dynamic UserInterface (DUI) within an application. The sequence of steps shown inFIG. 2A may differ among embodiments of the invention, and one or moreof the steps may be performed in parallel and/or may be optional.Accordingly, the scope of the invention should not be considered limitedto the specific arrangement of steps shown in FIG. 2A.

In STEP 205, the transaction relating to a customer of the user isreceived. It may be received from a user of the application. Thetransaction may be, for example, a bill to a customer owed to the userfor products sold to the customer.

In STEP 210, a request to generate a form for the transaction isreceived. It may be received from the user and within the application.The request may be, for example, initiated by the user via a mouse clickin the application.

In STEP 215, the form is generated containing a customer list and a formelement. It may be generated based on the request to generate the formand within the application. The customer list may contain a completelist of the customers of the user's business. The form element may be,for example, a shipping address of a customer.

In STEP 220, a request to generate the DUI is received. It may bereceived from the user and within the application. The request may be,for example, initiated by the user via a selection of an icon in theapplication.

In STEP 225, the DUI is generated adjacent to the form and displayedwithin the application. It may be generated based on the request togenerate the DUI. The DUI may contain various transaction visuals, eachrepresenting a transaction.

In STEP 230, an identification of the customer is received from thecustomer list. It may be received from the user and within the formadjacent to the DUI. For example, the user may select an individualcustomer from the customer list in the form.

In STEP 235, the DUI is populated with the transaction relating to thecustomer. The transaction may be owned by an application operator, andthe form may be populated based on the identification of the customer.The DUI may be populated with a number of transactions, each relating tothe customer.

In STEP 240, a selection of the transaction is received from the DUI. Itmay be received from the user. For example, the user may select one outof a number of transactions by dragging it and dropping it into theform.

In STEP 245, the form element is populated using the transaction. It maybe populated within the form adjacent to the DUI. The form element maybe automatically populated with or without a selection of the formelement by the user.

In STEP 250, the transaction is recorded. It may be recorded within theapplication. The transaction may also be recorded within a datarepository operatively connected to the application.

FIG. 2B shows a flowchart in accordance with one or more embodiments ofthe invention. The process shown in FIG. 2B may be used, for example,with the system (100), to record a transaction using a DUI within anapplication. The sequence of steps shown in FIG. 2B may differ amongembodiments of the invention, and one or more of the steps may beperformed in parallel and/or may be optional. Accordingly, the scope ofthe invention should not be considered limited to the specificarrangement of steps shown in FIG. 2B.

In STEP 255, a second transaction is received. It may be received fromthe user. The second transaction may be, for example, a promotion usedby a customer.

In STEP 256, the transaction and the second transaction are categorizedto order the transaction and the second transaction. The transactionsmay be ordered, for example, alphanumerically according to their titles.For example, if the first transaction is called “expenses”, and thesecond transaction is called “promotions”, then the ordering would be“expenses” followed by “promotions”.

In STEP 257, the DUI is populated with the transaction and the secondtransaction according to the order. Specifically, the transactions maybe displayed in the DUI according to their ordering. For example, if theorder is “expenses” followed by “promotions”, then the “expenses”transaction may be displayed above the “promotions” transaction in theDUI.

In STEP 258, an invoice is received relating to a customer of the user.It may be received from the user and within the application. The invoicemay relate to products and/or services purchased by the customer fromthe user.

In STEP 259, the DUI is populated with the invoice. It may be populatedwithin the application. For example, the details of the invoice may beinput into the DUI.

In STEP 260, a third party transaction is received. It may be receivedfrom a third party and within the application. The third partytransaction may be any transaction relating to the user and/or customer.

In STEP 261, the DUI is populated with the third party transaction. Itmay be populated automatically and without intervention from the user.For example, the details of the third party transaction may be inputinto the DUI.

In STEP 262, a recurring transaction relating to the user is identified.It may be identified within the application. The recurring transactionmay be any transaction that occurs repeatedly within a time interval.For example, it may be a bill to a customer that occurs once a month.

In STEP 263, the recurring transaction is obtained. It may be obtainedby the application, from the customer, the user, or a third party.

In STEP 264, the DUI is populated with the recurring transaction. It maybe populated automatically and without intervention of the user. Forexample, the details of the recurring transaction may be input into theDUI.

In STEP 265, an expense relating to the user is received. It may bereceived from the user and within the application. The expense mayrelate, for example, to a product purchased by the user on behalf of thecustomer.

In STEP 266, the DUI is populated with the expense. It may be populatedwithin the application. For example, the details of the expense may beinput into the DUI.

In STEP 267, a timecard of an employee of the user is received. It maybe received from the user and within the application. The timecard mayindicate a number of hours worked by an employee of the user's business.

In STEP 268, the DUI is populated with the timecard. It may be populatedwithin the application. For example, the details of the timecard may beinput into the DUI.

In STEP 269, a selection of a company is received within the form. Itmay be received from the user. The company may be a client and/orpartner of the user's business.

In STEP 270, the DUI is populated with transactions relating to thecompany. It may be populated based on the selection. For example, thedetails of the transactions relating to the company may be input intothe DUI.

In STEP 271, a request is received to close the DUI. The request may bereceived from the user and within the application.

In STEP 272, it is determined if the user wants to close the DUI. If theuser in fact does want to close the DUI, the process proceeds to STEP273, otherwise the process ends.

In STEP 273, the DUI is closed by sliding the DUI off the application.The DUI may be closed based on the request.

Those skilled in the art will appreciate that the form may be related toa transaction of a customer, a company, an employee, the user'sbusiness, or various other entities associated with the businessconcerns of the user. Further, the DUI may other types of content beyondthe transaction described, such as information about clients andvendors, tax documents, sales orders, contracts, bills, invoices,images, credit memos, purchase orders, estimates, credits, timesheets,billable time, billable expenses, billable charges, and attachments. Thetransactions and other data in the DUI enhance the ease of use andmaintain a high relevance with the contents and focus of the form.Essentially, the DUI may populate with transactions that are related tothe specific action taken by the user, and the specific form selected bythe user. Each transaction may have a visual representation in the DUI.Once a transaction is copied to the form from the DUI, the visualrepresentation of it may disappear from the DUI, although it may thenagain be populated in the DUI at a later time.

FIG. 3 shows an example in accordance with one or more embodiments ofthe invention. The example shown in FIG. 3 may be used, for example,with the system (100), to generate a form. The elements shown in FIG. 3may differ among embodiments of the invention, and one or more of theelements may be optional.

In FIG. 3, a create menu (305) includes various types (340) of entitiesfor form creation, including customers (306), vendors (307), employees(308), and other (309). The customers (306) type may include variousform types, including but not limited to invoice (310), receive payment(311), estimate (312), credit memo (313), sales receipt (314), refundreceipt (315), delayed credit (316), and delayed charge (317). Thevendors (307) type may include various form types, including expense(320), check (321), bill (322), pay bills (323), purchase order (324),vendor credit (325), and credit card credit (326). The employees (308)type may include various form types, including paycheck (330), singletime activity (331), and weekly timesheet (332). The other (309) typemay also include various form types, such as bank deposit (335),transfer (336), journal entry (337), and statement (338). Those skilledin the art will appreciate that there may be various other types offorms that may be created through the create menu (305) that have notbeen disclosed.

FIG. 4 shows an example in accordance with one or more embodiments ofthe invention. The example shown in FIG. 4 may be used, for example,with the system (100), to drag and drop a transaction from a DUI to aform. The elements shown in FIG. 4 may differ among embodiments of theinvention, and one or more of the elements may be optional.

In FIG. 4, a form (405) for an invoice is shown. The form (405) containsvarious elements, including a company list (406) containing a list ofcompanies related to the user's business, a form element (407) relatingto a billing address of the company, a form element (408) relating tothe shipping address of the company, a form element (409) relating to aproduct and/or service of the invoice, a form element (410) relating toa description of the product and/or service of the invoice, a balancedue (411), and other elements such as an email address of the company,an online payment options with various credit cards, terms of theinvoice, an invoice date, a due date, shipping details (e.g. carrier,date, tracking number), a sales representative identity, a customer IDnumber, a quantity, rate, amount, tax, and service date of the productand/or service of the invoice, and a subtotal. Those skilled in the artwill appreciate that there may be various other form elements, and thatthere may be various other form types that are not described.

FIG. 4 also shows a DUI (415) positioned to the right of the form (405).The DUI (415) contains various transactions, such as transaction (416)relating to an estimate for a charge to a customer, a billable time(417) relating to an amount owed by a customer to the user for timespent on a service, and a billable expense (418) relating to an expenseincurred on behalf of a customer by the user's business. A close button(420) allows a user to close the DUI (415) and slide it off the invoiceform (405). Those skilled in the art will appreciate that thetransactions in the DUI (415) may relate to another category beyond acustomer, such as a business or an employee, or even the user's businessitself. Further, the transactions may be ordered in the DUI (415)according to their names, a monetary amount, a calendar date, and soforth.

Embodiments of the invention may be implemented on virtually any type ofcomputing system regardless of the platform being used. For example, thecomputing system (500) may be one or more mobile devices (e.g., laptopcomputer, smart phone, personal digital assistant, tablet computer, orother mobile device), desktop computers, servers, blades in a serverchassis, or any other type of computing device or devices that includesat least the minimum processing power, memory, and input and outputdevice(s) to perform one or more embodiments of the invention. Forexample, as shown in FIG. 5, the computing system (500) may include oneor more computer processor(s) (802), associated memory (504) (e.g.,random access memory (RAM), cache memory, flash memory, etc.), one ormore storage device(s) (506) (e.g., a hard disk, an optical drive suchas a compact disk (CD) drive or digital versatile disk (DVD) drive, aflash memory stick, etc.), and numerous other elements andfunctionalities. The computer processor(s) (502) may be an integratedcircuit for processing instructions. For example, the computerprocessor(s) may be one or more cores, or micro-cores of a processor.The computing system (500) may also include one or more input device(s)(510), such as a touchscreen, keyboard, mouse, microphone, touchpad,electronic pen, or any other type of input device. Further, thecomputing system (500) may include one or more output device(s) (508),such as a screen (e.g., a liquid crystal display (LCD), a plasmadisplay, touchscreen, cathode ray tube (CRT) monitor, projector, orother display device), a printer, external storage, or any other outputdevice. One or more of the output device(s) may be the same or differentfrom the input device(s). The computing system (500) may be connected toa network (512) (e.g., a local area network (LAN), a wide area network(WAN) such as the Internet, mobile network, or any other type ofnetwork) via a network interface connection (not shown). The input andoutput device(s) may be locally or remotely (e.g., via the network(512)) connected to the computer processor(s) (502), memory (504), andstorage device(s) (506). Many different types of computing systemsexist, and the aforementioned input and output device(s) may take otherforms.

Software instructions in the form of computer readable program code toperform embodiments of the invention may be stored, in whole or in part,temporarily or permanently, on a non-transitory computer readable mediumsuch as a CD, DVD, storage device, a diskette, a tape, flash memory,physical memory, or any other computer readable storage medium.Specifically, the software instructions may correspond to computerreadable program code that when executed by a processor(s), isconfigured to perform embodiments of the invention.

Further, one or more elements of the aforementioned computing system(500) may be located at a remote location and connected to the otherelements over a network (512). Further, embodiments of the invention maybe implemented on a distributed system having a plurality of nodes,where each portion of the invention may be located on a different nodewithin the distributed system. In one embodiment of the invention, thenode corresponds to a distinct computing device. Alternatively, the nodemay correspond to a computer processor with associated physical memory.The node may alternatively correspond to a computer processor ormicro-core of a computer processor with shared memory and/or resources.

While the invention has been described with respect to a limited numberof embodiments, those skilled in the art, having benefit of thisdisclosure, will appreciate that other embodiments can be devised whichdo not depart from the scope of the invention as disclosed herein.Accordingly, the scope of the invention should be limited only by theattached claims.

What is claimed is:
 1. A method for recording a transaction using aDynamic User Interface (DUI) within an application, comprising:identifying, within the application, a prior transaction relating to acustomer of a user; obtaining, in response to identifying the priortransaction and by the application, the prior transaction; automaticallypopulating, without intervention of the user, the DUI with the priortransaction such that one or more details of the prior transaction areinput to the DUI; receiving, from the user and within the application, arequest to generate a form for the transaction; generating, in responseto receiving the request to generate the form and within theapplication, the form comprising a customer list and a form element;receiving, from the user and within the application, a request togenerate the DUI; generating, in response to receiving the request togenerate the DUI, the DUI adjacent to the form displayed within theapplication; receiving, from the user and within the form adjacent tothe DUI, an identification of the customer from the customer list;without intervention of the user and in response to receiving theidentification of the customer, displaying within the DUI the priortransaction relating to the customer, wherein the prior transaction isowned by an application operator; receiving, from the user, a selectionof therp for transaction from the DUI by receiving, from the user, adrag and drop manipulation of a visual representation of the priortransaction from the DUI to the form adjacent to the DUI; populating, inresponse to receiving the selection of the prior transaction and withinthe form adjacent to the DUI, the form element using therp fortransaction; in response to populating the form element, temporarilyhiding the visual representation of the prior transaction from the DUI;and recording, within the application, the transaction.
 2. The method ofclaim 1, further comprising: identifying, within the application, arecurring transaction relating to the user; obtaining, by theapplication, the recurring transaction; and populating, withoutintervention of the user, the DUI with the recurring transaction.
 3. Themethod of claim 1, further comprising: receiving, from the user andwithin the application, an expense relating to the user; and populating,within the application, the DUI with the expense.
 4. The method of claim1, wherein the transaction relates to a purchase order.
 5. The method ofclaim 1, further comprising: receiving, from the user and within theapplication, a timecard of an employee of the user; and populating,within the application, the DUI with the timecard.
 6. The method ofclaim 1, further comprising: receiving, from the user and within theapplication, a request to close the DUI; and closing, based on therequest, the DUI by sliding the DUI off the application.
 7. The methodof claim 1, further comprising: receiving, from the user, a selection ofa company within the form; and populating, based on the selection, theDUI with a plurality of transactions relating to the company.
 8. Themethod of claim 1, further comprising: receiving, from the user, asecond transaction; categorizing the transaction and the secondtransaction to order the transaction and the second transaction; andpopulating the DUI with the transaction and the second transactionaccording to the order.
 9. The method of claim 1, further comprising:receiving, from the user and within the application, an invoice relatingto the customer of the user; and populating, within the application, theDUI with the invoice.
 10. The method of claim 1, further comprising:receiving, from a third party and within the application, a third partytransaction; populating, without intervention from the user, the DUIwith the third party transaction.
 11. A system for recording atransaction using a Dynamic User Interface (DUI), comprising: a firstservice provider server comprising: a computer processor, and anapplication executing on the computer processor, with functionality toperform: identifying, within the application, a prior transactionrelating to a customer of a user, obtaining, in response to identifyingthe prior transaction, the prior transaction, automatically populating,without intervention of the user, the DUI with the prior transactionsuch that one or more details of the prior transaction are input to theDUI, receiving, from the user and within the application, a request togenerate a form for the transaction, generating, in response toreceiving the request to generate the form and within the application,the form comprising a customer list and a form element, receiving, fromthe user and within the application, a request to generate the DUI,generating, in response to receiving the request to generate the DUI,the DUI adjacent to the form displayed within the application,receiving, from the user and within the form adjacent to the DUI, anidentification of the customer from the customer list, withoutintervention of the user and in response to receiving the identificationof the customer, displaying within the DUI the prior transactionrelating to the customer, wherein the prior transaction is owned by anapplication operator, receiving, from the user, a selection of the priortransaction from the DUI by receiving, from the user, a drag and dropmanipulation of a visual representation of the prior transaction fromthe DUI to the form adjacent to the DUI, populating, in response toreceiving the selection of therp for transaction and within the formadjacent to the DUI, the form element using the prior transaction, inresponse to populating the form element, temporarily hiding the visualrepresentation of the prior transaction from the DUI, and recording,within the application, the transaction; and a second service providerserver communicatively coupled to the first service provider server andcomprising a data repository storing the transaction.
 12. The system ofclaim 11, wherein the application comprises further functionality toperform: identifying, within the application, a recurring transactionrelating to the user; obtaining, by the application, the recurringtransaction; and populating, without intervention of the user, the DUIwith the recurring transaction.
 13. The system of claim 11, wherein theapplication comprises further functionality to perform: receiving, fromthe user and within the application, an expense relating to the user;and populating, within the application, the DUI with the expense. 14.The system of claim 11, wherein the application comprises furtherfunctionality to perform: receiving, from the user and within theapplication, a timecard of an employee of the user; and populating,within the application, the DUI with the timecard.
 15. The system ofclaim 11, wherein the application comprises further functionality toperform: receiving, from the user and within the application, a requestto close the DUI; and closing, based on the request, the DUI by slidingthe dynamic UI off the application.
 16. The system of claim 11, whereinthe application comprises further functionality to perform: receiving,from the user, a selection of a company within the form; and populating,based on the selection, the DUI with a plurality of transactionsrelating to the company.
 17. The system of claim 11, wherein theapplication comprises further functionality to perform: receiving, fromthe user, a second transaction; categorizing the transaction and thesecond transaction to order the transaction and the second transaction;and populating the DUI with the transaction and the second transactionaccording to the order.
 18. The system of claim 11, wherein theapplication comprises further functionality to perform: receiving, fromthe user and within the application, an invoice relating to the customerof the user; and populating, within the application, the DUI with theinvoice.
 19. The system of claim 11, wherein the application comprisesfurther functionality to perform: receiving, from a third party andwithin the application, a third party transaction; populating, withoutintervention from the user, the DUI with the third party transaction.20. A non-transitory computer readable storage medium storinginstructions for recording a transaction using a Dynamic User Interface(DUI) within an application, the instructions executable on a computerprocessor and comprising functionality for: identifying, within theapplication, a prior transaction relating to a customer of a user;obtaining, in response to identifying the prior transaction and by theapplication, the prior transaction; automatically populating, withoutintervention of the user, the DUI with the prior transaction such thatone or more details of the prior transaction are input to the DUI;receiving, from the user and within the application, a request togenerate a form for the transaction; generating, in response toreceiving the request to generate the form and within the application,the form comprising a customer list and a form element; receiving, fromthe user and within the application, a request to generate the DUI;generating, in response to receiving the request to generate the DUI,the DUI adjacent to the form displayed within the application;receiving, from the user and within the form adjacent to the DUI, anidentification of the customer from the customer list; withoutintervention of the user and in response to receiving the identificationof the customer, displaying within the DUI the prior transactionrelating to the customer, wherein the prior transaction is owned by anapplication operator; receiving, from the user, a selection of the priortransaction from the DUI by receiving, from the user, a drag and dropmanipulation of a visual representation of the prior transaction fromthe DUI to the form adjacent to the DUI; populating, in response toreceiving the selection of the prior transaction and within the formadjacent to the DUI, the form element using the prior transaction; inresponse to populating the form element, temporarily hiding the visualrepresentation of the prior transaction from the DUI; and recording,within the application, the transaction.
 21. The non-transitory computerreadable storage medium of claim 20, the instructions further comprisingfunctionality for: identifying, within the application, a recurringtransaction relating to the user; obtaining, by the application, therecurring transaction; and populating, without intervention of the user,the DUI with the recurring transaction.
 22. The non-transitory computerreadable storage medium of claim 20, the instructions further comprisingfunctionality for: receiving, from the user and within the application,an expense relating to the user; and populating, within the application,the DUI with the expense.
 23. The non-transitory computer readablestorage medium of claim 20, the instructions further comprisingfunctionality for: receiving, from the user and within the application,a timecard of an employee of the user; and populating, within theapplication, the DUI with the timecard.
 24. The non-transitory computerreadable storage medium of claim 20, the instructions further comprisingfunctionality for: receiving, from the user and within the application,a request to close the DUI; and closing, based on the request, the DUIby sliding the DUI off the application.
 25. The non-transitory computerreadable storage medium of claim 20, the instructions further comprisingfunctionality for: receiving, from the user, a selection of a companywithin the form; and populating, based on the selection, the DUI with aplurality of transactions relating to the company.